<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>NetOps</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/NetOps"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-NetOps rootpage-NetOps skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">NetOps</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><p><b>NetOps</b> is defined as the operational framework consisting of three essential tasks, <a href="Situation_awareness" title="Situation awareness">Situational Awareness (SA)</a>, and <a href="Command_and_Control" class="mw-redirect" title="Command and Control">Command & Control (C2)</a> that the Commander (CDR) of US Strategic Command (USSTRATCOM), in coordination with DoD and Global NetOps Community, employs to <i><b>operate, manage and defend</b></i> the <a href="Global_Information_Grid" title="Global Information Grid">Global Information Grid</a> (GIG) to ensure information superiority for the United States.<sup id="cite_ref-conops_1-0" class="reference"><a href="#cite_note-conops-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p><p>DoD Instruction (DoDI) 8410.02 defines NetOps as the DoD-wide operational, organizational, and technical capabilities for operating and defending the Global Information Grid. NetOps includes, but is not limited to, enterprise management, net assurance, and content management. NetOps provides Combatant Commanders (COCOMs) with GIG Situational Awareness to make informed Command and Control decisions. GIG SA is gained through the operational and technical integration of enterprise management and defense actions and activities across all levels of command (strategic, operational and expeditionary forces).<sup id="cite_ref-dodi_2-0" class="reference"><a href="#cite_note-dodi-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>
</p>
<p>The three essential tasks are as follows:
</p>
<ul><li>GIG Enterprise Management (GEM)</li>
<li>GIG Net Assurance (GNA)</li>
<li>GIG Content Management (GCM)<sup id="cite_ref-dodi_2-1" class="reference"><a href="#cite_note-dodi-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup></li></ul>
<p>The synergy achieved by each integrated relationship between any two of the essential tasks (GEM, GNA, and GCM) produces the following NetOps desired effects in support of the overall goal of NetOps which is to provide the right information to the edge:
</p>
<ul><li>Assured System and Network Availability</li>
<li>Assured Information Protection</li>
<li>Assured Information Delivery<sup id="cite_ref-conops_1-1" class="reference"><a href="#cite_note-conops-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup></li></ul>
<p>The element of NetOps known as Situational Awareness (SA), is the primary ability to improve the quality and timeliness of collaborative decision-making. To be effective, much of the SA must be shared in near-real-time by the decision-makers who have the ability to take this information, conduct critical analysis and act on those decisions with regards to employment, protection and defense of the GIG.
</p><p>This shared Situational Awareness is derived from common reporting requirements using functionally standardized management tools and common data information exchange formats across the Defense Department. These capabilities collect (or receive), and fuse (enterprise management, network defense and configuration management) data in a real time or near real-time fashion to produce defined views of the mission critical GIG information of concern to a commander or NetOps center.
</p><p>The DoD NetOps Community strives to obtain common visibility of network resources so that these can be managed, anticipate and mitigate problems, ensuring uninterrupted availability and protection of the GIG and provide for graceful degradation, self-healing, failover, diversity, and elimination of critical failure points. Through effective visibility, the NetOps community endeavors to attain the three goals of NetOps: Assured System and Network Availability, Assured Information Protection and Assured Information Delivery.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>
</p>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="Joint_Task_Force_Global_Network_Operations_(JTF-GNO)">Joint Task Force Global Network Operations (JTF-GNO)</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1236090951">
/* start https://en.wikipedia.org/ */
.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}
/* end https://en.wikipedia.org/ */
</style><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">Joint Task Force-Global Network Operations</a></div>
<p>JTF-GNO directs the operation and defense of the GIG to assure timely and secure Net-Centric capabilities across strategic, operational, and expeditionary boundaries in support of full spectrum warfighting, intelligence, and business missions for the Defense Department.
<sup id="cite_ref-stratcom_4-0" class="reference"><a href="#cite_note-stratcom-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="Background">Background</h2></div>
<p>In 1998, the <a href="United_States_Department_of_Defense" title="United States Department of Defense">Department of Defense</a> recognized a growing cyber threat and in response created the Joint Task Force — Computer Network Defense (JTF-CND), which achieved Initial Operational Capability (IOC) on 30 December 1998 and Full Operational Capability (FOC) by June 1999.
</p><p>In the fall of 2000, in accordance with <a href="United_States_Department_of_Defense" title="United States Department of Defense">DoD</a> doctrine, JTF-CND became the Joint Task Force — Computer Network Operations (JTF-CNO). In October 2002, the new Unified Command Plan (UCP), Change 2, re-aligned JTF-CNO under the <a href="STRATCOM" class="mw-redirect" title="STRATCOM">United States Strategic Command (USSTRATCOM)</a>.
</p><p>The JTF-CNO began its largest and most comprehensive transformation in April 2004 when the Commander of <a href="STRATCOM" class="mw-redirect" title="STRATCOM">US Strategic Command</a> approved the Joint Concept of Operations for <a href="Global_Information_Grid" title="Global Information Grid">GIG</a> Network Operations. This “NetOps CONOPS” provided the common framework and command and control structure to conduct the USSTRATCOM Unified Command Plan (UCP) - assigned mission of Global Network Operations (NETOPS), combining the disciplines of Enterprise Systems (EM) and Network Management (NM), Computer Network Defense (CND), and Information Dissemination Management (IDM).
</p><p>The <a href="United_States_Secretary_of_Defense" title="United States Secretary of Defense">Secretary of Defense</a> signed a delegation of authority letter on 18 June 2004, designating the Director, <a href="Defense_Information_Systems_Agency" title="Defense Information Systems Agency">DISA</a> as the new Commander of the <a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">Joint Task Force-Global Network Operations</a>. With this designation, the new command assumed the responsibility for directing the operation and defense of the <a href="Global_Information_Grid" title="Global Information Grid">GIG</a>.
</p><p>This transformation enhanced the <a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">JTF GNO's</a> mission and objectives in achieving the Joint Vision 2020 Objective Force and the evolving concept of Net-Centricity.
</p><p>As new concepts such as <a href="Network-centric_warfare" title="Network-centric warfare">Network-centric warfare</a> and Joint Vision 2010<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> arrived in the mid 1990s, it became clear that the center of gravity for U.S. military warfighting capability was shifting towards the network. A corresponding capability was required to move beyond managing the network as a back-office system into a domain of warfighting.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>
</p><p>NetOps was originally developed under the leadership of then <a href="United_States_Pacific_Command" class="mw-redirect" title="United States Pacific Command">United States Pacific Command</a> J6 <a href="Brigadier_General" class="mw-redirect" title="Brigadier General">Brigadier General</a> James Bryan during the stand-up of the <a href="Commander_United_States_Pacific_Fleet" class="mw-redirect" title="Commander United States Pacific Fleet">USCINCPAC</a> Theater C4I Coordination Center (TCCC) at <a href="Camp_H._M._Smith" title="Camp H. M. Smith">Camp H. M. Smith</a>, Hawaii in 1999.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> The TCCC initiative was constructed of two distinct components - the technology that formed the vision of the <a href="Global_Information_Grid" title="Global Information Grid">GIG</a> and the NetOps initiative; and the partnerships that made it a reality.
</p><p>Through its working relationships with <a href="Defense_Information_Systems_Agency" title="Defense Information Systems Agency">DISA</a>, the Service Components, Sub-Unified Commands, JTFs, other CINC TCCC's, and the <a href="Joint_Chiefs_of_Staff" title="Joint Chiefs of Staff">Joint Staff</a>, <a href="Commander_United_States_Pacific_Fleet" class="mw-redirect" title="Commander United States Pacific Fleet">USCINCPAC</a> TCCC made the initial strides towards achieving Information Superiority and true enterprise-level processes. The <a href="Commander_United_States_Pacific_Fleet" class="mw-redirect" title="Commander United States Pacific Fleet">USCINCPAC</a> TCCC was a pilot program for the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASD/C3I) NetOps concept. The NetOps concept began with the development of the architectural framework for NetOps, and a <a href="Commander_United_States_Pacific_Fleet" class="mw-redirect" title="Commander United States Pacific Fleet">USCINCPAC</a> developed <a href="Concept_of_Operations" class="mw-redirect" title="Concept of Operations">Concept of Operations (CONOPS)</a> outlining the key players and their roles and responsibilities necessary to develop the NetOps construct in the Pacific Theater. <sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>
</p><p>The original NetOps construct consisted of Network Management (NM), Information Assurance (IA), and Information Dissemination Management (IDM). Today the construct has evolved into GIG Enterprise Management (GEM), GIG Net Assurance(GNA), and GIG Content Management which roughly equates to the intent of the original NetOps concept.<sup id="cite_ref-dodi_2-2" class="reference"><a href="#cite_note-dodi-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="NetOps_Vision">NetOps Vision</h2></div>
<p>“We must change the paradigm in which we talk and think about the network; we must ‘fight’ rather than ‘manage’ the network and operators must see themselves as engaged at all times, ensuring the health and operation of this critical weapons system.” <a href="Donald_Rumsfeld" title="Donald Rumsfeld">Donald Rumsfeld</a>, <a href="United_States_Secretary_of_Defense" title="United States Secretary of Defense">United States Secretary of Defense</a> (2001 - 2006)
</p><p>"The US government and the US military must become still more joint, more agile, more decentralized, more networked, and better arranged to share information and coordinate actions." <sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> <a href="Donald_Rumsfeld" title="Donald Rumsfeld">Donald Rumsfeld</a>, <a href="United_States_Secretary_of_Defense" title="United States Secretary of Defense">United States Secretary of Defense</a> (2001 - 2006)
</p><p>“This version of the NetOps CONOPS documents the lessons learned by <a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">Joint Task Force-Global Network Operations</a> and the NetOps community through operations, exercises, and other events. We will continue to work with the NetOps Community as we translate the concepts set forth in this document into doctrine, policy and joint tactics, techniques, and procedures that strengthen the operations and defense of the Global Information Grid in support of warfighter business and intelligence operations.” <a href="General_James_E._Cartwright" class="mw-redirect" title="General James E. Cartwright">General James E. Cartwright</a>, Commander, <a href="United_States_Strategic_Command" title="United States Strategic Command">United States Strategic Command</a>(2004- August 2007)<sup id="cite_ref-conops_1-2" class="reference"><a href="#cite_note-conops-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p><p>“The Strategic Vision for the <a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">JTF GNO</a> is to lead an adaptive force that assures the availability, delivery, and protection of the <a href="Global_Information_Grid" title="Global Information Grid">Global Information Grid</a>. The NetOps framework, effects, and organizational relationships described herein formulate a foundation for the operational future of the GIG, but these will not happen automatically, nor will they occur without significant effort from the entire NetOps Community. Attaining the vision will require cooperation, innovation, and execution from all mission partners and everyone who touches the GIG.” (From <i>"<a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">Joint Task Force-Global Network Operations</a> Strategic Plan, An Adaptive Force Ensuring Information Delivery"</i>, February 2006. The adaptive force assures availability, delivery and protection of infrastructure, systems, and information.) LtGen Charles E. Croom, Commander, <a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">JTF GNO</a>.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>
</p><p>There is also a new paradigm shift occurring in NetOps from 1.0 to 2.0, or DevOps. <a rel="nofollow" class="external text" href="https://netopstransformation.com">NetOps Transformation</a> is part of a new wave of automation assistance for network operators, and there are a few methodologies out there to help others. One prominent methodology is aptly named DIRE NetOps. It focuses on Documentation, Isolation, Repair, and Escalation to guide the user through the transformation process, ensuring high value tasks are supported with automation.
</p>
<div class="mw-heading mw-heading2"><h2 id="Mission">Mission</h2></div>
<p>The NetOps mission is to operate and defend the <a href="Global_Information_Grid" title="Global Information Grid">GIG</a>. Unlike many missions with a defined completion date, NetOps has been established as a standing Joint Force mission necessitating dedicated leadership and resources to execute.
</p><p>NetOps provides assured NetCentric services to the DoD in support of full spectrum of warfighting operations, intelligence, and business missions throughout the <a href="Global_Information_Grid" title="Global Information Grid">GIG</a> enterprises, seamlessly, end-to-end. An objective of NetCentric services is to quickly get information to decision makers, with adequate context, to make better decisions affecting the mission and to project their decisions forward to their forces for action.
</p><p>If the decision maker is not getting the needed net-centric services, the GIG NetOps community must collaboratively determine who must take action and how information flow can be optimized. This requires NetOps personnel to have a shared SA as well as the technologies, procedures, and collaborative organizational structures to rapidly assess and respond to system and network degradations, outages, or changes in operational priorities. All functions required to most effectively support GIG operations will be holistically managed. <sup id="cite_ref-conops_1-3" class="reference"><a href="#cite_note-conops-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p><p>The effectiveness of NetOps will be measured in terms of availability and reliability of net-centric services, across all domains, in adherence to agreed-upon service levels and policies. The method for service assurance in a NetCentric collaborative environment is to establish operational thresholds, compliance monitoring, and a clear understanding of the capabilities between enterprise service/resource providers and consumers through Service Level Agreements (SLAs).
</p><p>Proper instrumentation of the <a href="Global_Information_Grid" title="Global Information Grid">GIG</a> will enable monitoring of adherence to these SLAs, as well as enable timely decision-making, service prioritization, resource allocation, root cause, and mission impact assessment. Subsequent TTPs and SLAs will be formalized with appropriate implementation policies to enforce compliance.<sup id="cite_ref-conops_1-4" class="reference"><a href="#cite_note-conops-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2></div>
<ul><li><a href="Joint_Task_Force-Global_Network_Operations" class="mw-redirect" title="Joint Task Force-Global Network Operations">Joint Task Force-Global Network Operations</a></li>
<li><a href="United_States_Strategic_Command" title="United States Strategic Command">United States Strategic Command</a></li>
<li><a href="United_States_Cyber_Command" title="United States Cyber Command">United States Cyber Command</a></li>
<li><a href="Global_Information_Network_Architecture" title="Global Information Network Architecture">Global Information Network Architecture</a></li>
<li><a href="Information_Assurance_Vulnerability_Alert" class="mw-redirect" title="Information Assurance Vulnerability Alert">Information Assurance Vulnerability Alert</a></li></ul>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */
.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}
/* end https://en.wikipedia.org/ */
</style><div class="reflist">
<div class="mw-references-wrap"><ol class="references">
<li id="cite_note-conops-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-conops_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-conops_1-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-conops_1-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-conops_1-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-conops_1-4"><sup><i><b>e</b></i></sup></a></span> <span class="reference-text">Joint Concept of Operations (CONOPS) for Global Information Grid (GIG) NetOps Version 3, dated August 4, 2006</span>
</li>
<li id="cite_note-dodi-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-dodi_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-dodi_2-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-dodi_2-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110106090414/http://www.dtic.mil/whs/directives/corres/pdf/841002p.pdf">DoDI 8410.02, NetOps for the Global Information Grid (GIG), dated December 19, 2008</a></span>
</li>
<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://www.cert.mil/">JTF-GNO Website, December 2008</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070323125238/http://www.cert.mil/">Archived</a> 2007-03-23 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>
</li>
<li id="cite_note-stratcom-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-stratcom_4-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.stratcom.mil/">United States Strategic Command Official Website</a></span>
</li>
<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */
.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}
/* end https://en.wikipedia.org/ */
</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20161224220150/http://www.dtic.mil/jv2010/jv2010.pdf">"Joint Vision 2010"</a> <span class="cs1-format">(PDF)</span>. Archived from <a rel="nofollow" class="external text" href="http://www.dtic.mil/jv2010/jv2010.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2016-12-24<span class="reference-accessdate">. Retrieved <span class="nowrap">2008-03-29</span></span>.</cite></span>
</li>
<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.oft.osd.mil/initiatives/ncw/docs/NCW_Origins_and_Future.doc">Network-Centric Warfare: Its Origin and Future, By Vice Admiral Arthur K. Cebrowski, U.S. Navy, and John J. Garstka, <i>Proceedings</i>, January 1998</a></span>
</li>
<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20060927230611/http://iac.dtic.mil/iatac/download/Vol3_No4.pdf">IA Newsletter, Volume 3, Number 4, USPACOM Theater Network Operations, Ensuring Information Superiority for the 21st Century</a></span>
</li>
<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20060927225833/http://iac.dtic.mil/iatac/download/Vol4_No4.pdf">IA Newsletter, Volume 4, Number 4, Partnership's - The Key to Success for Pacific Theater Network Operations (NetOps)</a></span>
</li>
<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://blog.wired.com/defense/2008/01/rummy-on-ncw.html">Secretary Rumsfeld speaking at a NetCentric Warfare Conference (NCW) 2008.</a></span>
</li>
<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text">JTF GNO Strategic Plan, An Adaptive Force Ensuring Information Delivery, February 2006</span>
</li>
</ol></div></div>
<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>
<ul><li><a rel="nofollow" class="external text" href="http://www.stratcom.mil/">United States Strategic Command Official Website</a></li>
<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20070323125238/http://www.cert.mil/">Joint Task Force Global Network Operations (JTF GNO) - Requires PKI/CAC</a></li>
<li><a rel="nofollow" class="external text" href="http://www.disa.mil/peo-ian/">Defense Information Systems Agency (DISA) Information Assurance/NetOps</a></li>
<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110906012808/http://iac.dtic.mil/iatac/ia_policychart.html">DoD IA Policy Chart - Build and Operate a Trusted GIG</a></li></ul></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2024-02-14" href="https://en.wikipedia.org/wiki/?title=NetOps&oldid=1207423589">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>
</body></html>